Rate Limits

These API requests are governed by rate limits that protect the stability and performance of the system:

Rate limits apply to a tenantClosed A secure, isolated KYX environment for a customer. Each tenant includes its own configuration, users, and transactions. A tenant belongs to a customer. A customer can have multiple tenants..

Authorization Requests

The default rate limit for Authorization requests for bearer tokens is 10 per second.

If the rate limit is reached a HTTP 429 Too many requests status code is returned.

Account Requests

The default rate limit for Account requests that initiate a new transaction is one per second, per tenant. The system builds in some flexibility to accommodate higher bursts for short durations, and you can contact Jumio Support if you require higher burst rates than the defaults allow.

If the rate limit is reached a HTTP 429 Too many requests status code is returned, as shown in the following example:

HTTP/1.1 429 Too Many Requests
Content-Type: application/json
{
    "title": "Too Many Requests",
    "status": 429,
    "detail": "Request limit exceeded"
}
Jumio Netverify customers that were not previously constrained by rate limits are now subject to default rate limits of 3 per second and 180 per minute for account requests.

Retrieval Requests

The default rate limit for requests to retrieve transaction details is fifteen per second, per tenant.

Jumio Netverify customers that were not previously constrained by rate limits are now subject to default rate limits of 45 per second and 2700 per minute for retrieval requests.